\chapter{Eliciting requirements}
\section{Introduction}
The \emph{Software Requirement Specification} document itself states in precise and explicit language those functions and 
capabilities a software system (i.e., a software application, an e-Commerce Web site, etc) must provide, as well as states 
any required constraints by which the system must abide. The SRS also functions as a blueprint for completing a project with as 
little cost growth as possible. The SRS is often referred to as the "parent" document because all subsequent project management 
documents, such as design specifications, statements of work, software architecture specifications, testing and validation plans, 
and documentation plans, are related to it. This definition was taken from \emph{\cite{SRSpecifiaction}}.

The SRS contains functional and non functional requirements:
\begin{itemize}
 \item \emph{Functional requirements} may be calculations, technical details, data manipulation and processing and other specific 
    functionality that define what a system is supposed to accomplish. Behavioural requirements describing all the cases where 
    the system uses the functional requirements are captured in use cases.
\item Functional requirements are supported by \emph{non-functional requirements} (also known as quality requirements), which 
    impose constraints on the design or implementation (such as performance requirements, security, or reliability). 
\end{itemize}
Generally, functional requirements are expressed in the form "system shall do \emph{requirement}", while non-functional 
requirements are "system shall be \emph{requirement}".  But in this report we focus on functional requirements of the first 
iteration which has been described on the planning report. This definition was taken from \emph{\cite{FuncNonFunctional}}.

\section{Functional requirements}
\subsection{Android application}
\input{Requirements/src/androidFunctionalRequirements}

\subsection{Web site application}
\input{Requirements/src/webSiteFunctionalRequirements}

\section{Non-functional requirements}
\input{Requirements/src/nonFunctionalRequirements}

\section{Requirements analysis}
\input{Requirements/src/requirementsAnalysis}